Managing host computing devices

ABSTRACT

Systems and methods are disclosed which facilitate the management of host computing devices through the utilization of a host computing device control component. The host computing device control component includes a state monitoring component that monitors operating states of the control component and a group of associated host computing devices. The state monitoring component includes a power supply separate from the control component power supply, a state processing component, a visual indicator interface, and a separate communication component to facilitate communication with other state monitoring components. Utilizing consensus type algorithms, the state monitoring components can decide information related to the set of host computing devices, such as a state monitoring component authoritative for the grouping of the host computing devices.

BACKGROUND

Generally described, computing devices utilize a communication network, or a series of communication networks, to exchange data. Companies and organizations operate computer networks that interconnect a number of computing devices to support operations or provide services to third parties. The computing systems can be located in a single geographic location or located in multiple, distinct geographic locations (e.g., interconnected via private or public communication networks). Specifically, data centers or data processing centers, herein generally referred to as a “data center,” may include a number of interconnected computing systems to provide computing resources to users of the data center. The data centers may be private data centers operated on behalf of an organization or public data centers operated on behalf, or for the benefit of, the general public.

To facilitate increased utilization of data center resources, virtualization technologies may allow a single physical computing device to host one or more instances of virtual machines that appear and operate as independent computing devices to users of a data center. Each single physical computing device can be generally referred to as a host computing device. With virtualization, the single physical computing device can create, maintain, delete, or otherwise manage virtual machines in a dynamic matter. In turn, users can request computer resources from a data center, including single computing devices or a configuration of networked computing devices, and be provided with varying numbers of virtual machine resources.

In conjunction with the utilization of virtualization technologies, data centers can physically organize sets of host computing devices to allow the host computing devices to share computing device resources, such as power or communication network connectivity. Such physical organization can correspond to physical racks in which the hosting computing devices are mounted, generally referred to as racks of host computing devices. As the number of racks of host computing devices increases, service providers associated with data centers have difficulty distinguishing between errors or faults associated with individual host computing devices, shared resources associated with a particular rack or distributed components utilized to manage the host computing devices. Additionally, in some scenarios, service providers may maintain multiple data centers. In such scenarios, the service providers would benefit from the determination of the availability of multiple data centers and the inter-data center synchronization of state information.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing aspects and many of the attendant advantages of this disclosure will become more readily appreciated as the same become better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:

FIG. 1 is a block diagram depicting an illustrative environment for managing host computing devices including a number of host computing devices and control components;

FIG. 2 is a block diagram illustrative of components of a control component for utilization in the environment for managing host computing devices of FIG. 1;

FIGS. 3A and 3B are block diagrams of the host computing device environment of FIG. 1 illustrating the processing of communication events and determination of communication event information in accordance with a consensus algorithm;

FIGS. 4A-4C are block diagrams of the host computing device environment of FIG. 1 illustrating a hierarchical exchange of event information in accordance with a consensus algorithm;

FIG. 5 is a flow diagram illustrative of a control component operating state processing routine implemented by a state monitoring component;

FIG. 6 is a flow diagram illustrative of an event management routine implemented by a state monitoring component; and

FIG. 7 is a flow diagram illustrative of an event subroutine implemented by a state monitoring component.

DETAILED DESCRIPTION

Generally described, aspects of the present disclosure relate to the management of host computing devices. Specifically, systems and methods are disclosed which facilitate the management of host computing devices through the utilization of a host computing device control component, or control component. A set of host computing devices can be organized into a logical grouping of host computing devices, such as corresponding to host computing devices in a physical rack or host computing devices within a data center. Additionally, a host computing device control component is associated with each logical grouping. In one aspect, the host computing device control component is in communication with the set of host computing devices to monitor performance or manage the operation of various aspects of the host computing devices in the corresponding rack. In another aspect, the control component includes a separate state monitoring component that monitors operating states of the control component and manages events associated with one or more the host computing devices. The state monitoring component includes a power supply separate from the control component power supply, a state processing component, a visual indicator interface, and a separate communication component to facilitate communication with other state monitoring components. Utilizing consensus type algorithms, the state monitoring components can decide information related to the set of host computing devices by agreement as to either the condition of the grouping of host computing devices or the designation of a state monitoring component authoritative for the grouping of host computing devices.

With reference now to FIG. 1, a block diagram depicting an illustrative host computing device environment 100 for managing host computing devices will be described. The host computing device environment 100 includes a plurality of host computing devices 102. Illustratively, the host computing devices 102 correspond to server computing device having one or more processors, memory, operating system and software applications that can be configured for a variety of purposes. Additionally, the host computing devices 102 may be configure to host one or more virtual machine instances. As illustrated in FIG. 1, the plurality of host computing devices 102 are organized according to a physical placement of a set of host computing devices, such as a rack or other support structure. The organization of each set of host computing devices 102 will be generally referred to as a rack 104. However, a grouping of host computing devices 102 can correspond to other structures or physical criteria as well as non-physical criteria.

In an illustrative embodiment, each rack 104 is associated with a host computing device control component 106, which can also be referred to as a rack control component. In an illustrative embodiment, a host computing device control component 106 can manage the operation of the set of host computing devices 102, or components thereof, including, but not limited to provisioning, updating, monitoring, and modifying software associated with the host computing devices. The host computing device control component 106 also includes a state monitoring component for monitoring the state of the operation of the host computing device control component 106 and providing visual indicators corresponding to the determined state of operation. Illustrative components of the host computing device control component 106 will be described with regard to FIG. 2. Additionally, the racks 104 can also be associated with one or more common computing resources 103, such as power sources, communication networks, and the like.

As illustrated in FIG. 1, the multiple racks 104 of host computing devices 102 may communicate via a communication network 108, such as a private or public network. For example, host computing device control components 106 from each rack 104 may be able to communicate with each other via the communication network 108, which can include a private communication network specific to host computing device control components. One skilled in the relevant art will appreciate that each rack 104 may include any number of host computing devices 102 and that the host computing device environment 100 can include any number of racks 104. Still further, the racks 104 may be further organized in a manner that does not require connectivity between all the racks in the host computing device environment.

Turning now to FIG. 2, illustrative components of a host computing device control component 106 in the host computing device environment 100 will be described. In an illustrative embodiment, the host computing device control component 106 can corresponds to a wide variety of computing devices including personal computing devices, laptop computing devices, hand-held computing devices, terminal computing devices, mobile devices (e.g., mobile phones, tablet computing devices, etc.), wireless devices, various electronic devices and appliances and the like. The content delivery environment 100 can include any of number and various kinds of host computing device control components 106, which may be customized according to specific racks 104 or types of racks.

Illustratively, the host computing device control component 106 may have varied local computing resources such as central processing units and architectures, memory, mass storage, graphics processing units, communication network availability and bandwidth, etc. Generally, however, each host computing device control component 106 may include various computing resources 202 that can include one or more processing units, such as one or more CPUs. The computing resources 202 may also include system memory, which may correspond to any combination of volatile and/or non-volatile storage mechanisms. The system memory may store information that provides an operating system component, various program modules, program data, or other components. The host computing device control component 106 performs functions by using the processing unit(s) to execute instructions provided by the system memory. The computing resources 202 may also include one or more input devices (keyboard, mouse device, specialized selection keys, touch screen interface, stylus, etc.) and one or more output devices (displays, printers, audio output mechanisms, etc.). The computing resources 202 may also include one or more types of removable storage and one or more types of non-removable storage. Still further, the computing resources can include hardware and software components for establishing communications over the communication network 108, such as a wide area network or local area network, or via an internal communication network connecting the set of host computing devices 102. For example, the host computing device control component 106 may be equipped with networking equipment and software applications that facilitate communications via the Internet or an intranet.

However, although various computing resources 202 have been identified, ones skilled in the relevant art will appreciate that various combinations of computing resources may be implemented on a host computing device control component 106 and that one or more of the identified computing resources may be optional.

As illustrated in FIG. 2, the host computing device control component 106 can include, among other hardware or software components, a management component 204 for facilitating management of the set of host computing devices 102. As discussed above, the management component 204 can facilitate various interactions with one or more of the set of host computing devices 102 including, but not limited to, provisioning, updating, monitoring, and modifying software associated with the host computing devices. Although the management component 204 is illustrated as a single component, one skilled in the relevant art will appreciate that the management component 204 may be made up of a number of components or subcomponents to carry out one or more management functions associated with the host computing device control component 106.

The host computing device control component 106 can also include a state monitoring component 206 for monitoring the state of the operation of the host computing device control component 106, communicating event information to other state monitoring components, and providing visual indicators corresponding to the determined state of operation. The state monitoring component 206 can include various components, or subcomponents (either hardware or software) for carrying out one or more of the functions of the state monitoring component. In one aspect, the state monitoring component 206 includes a power supply 208 for providing power to one or more components of the state monitoring component 206. Illustratively, the power supply 208 is independent of any power supply associated with the host computing device control component 106 such that a loss of power by the host computing device control component 106 does not result in a loss of power to the state monitoring component 206. For example, the power supply 208 may correspond to a battery or other capacitive device. The state monitoring component 206 can also include a state processing component 210 for determining an operating state of the rack control component based on one or more inputs provided to the state monitoring component 206 or based on a failure to receive inputs. The state monitoring component 206 can also determine various reboot parameters in the event of detection of a power event (e.g., a power outage or low power event) and initiate a reboot based on the reboot parameters.

The state monitoring component 206 can also include visual indicator interface component 212 for causing the generation of visual indicators, or other indicators, based on various determined operating states of the host computing device control component 106. In one embodiment, the visual indicator interface component 212 can include or be in direct communication with hardware for making the visual indications, including, but not limited to, liquid crystal displays (“LCD”), light emitting diodes (“LED”), sets of LCDs, sets of LEDs, multi-color LEDS, sets of multi-color LEDS and various combinations thereof. In another embodiment, the hardware for making the visual indications may be part of the computing resources 202 such that the visual indicator interface 212 is in communication (directly or indirectly) to cause the generation of various visual indicators as will be described below.

The state monitoring component 206 can further include a communication component 214 for establishing communications with other state monitoring components 204 or other reporting services as described in the present application. In an illustrative embodiment, the communication component 214 can include various hardware and software components utilized to exchange information via one or more communication paths. The communication paths can include wireless communication paths (via infrared, RF, optical, terrestrial, satellite communication media, etc.), wired communication paths, or a combination thereof. Although aspects of the present disclosure will be described with regard to an illustrative communication device environment and component interactions, communication protocols, flow diagrams and interfaces, one skilled in the relevant art will appreciate that the disclosed embodiments are illustrative in nature and should not be construed as limiting.

With reference now to FIGS. 3A and 3B various interactions between the components of the host computing device environment 100 will be described. For purposes of the illustrative embodiment, however, many of the components of the host computing device environment 100 have been omitted. Accordingly, one skilled in the relevant art will appreciate that additional or alternative components may be utilized in conjunction with the illustrated embodiments. With reference to FIG. 3A, the state monitoring component 206 of one or more host computing device control components 106 determines a communication event (1). Illustratively, a communication event can correspond to various faults or errors associated with the operation of individual host computing devices 102, grouping of host computing devices, or the host computing device control component 106. In another embodiment, the communication event can correspond to an exchange of status information without the occurrence of a fault or error.

In an illustrative embodiment, because the state monitoring component 206 of the host computing device control component 106 includes a separate power supply component 208, the state monitoring component 206 can continue to operate even if there is a disruption to the power supply provided to the host computing device control component 106 and set of host computing devices 102. Accordingly, the state monitoring component 206 then establishes an alternative network connection via the communication component 214. Illustratively, the state monitoring component 206 attempts to establish communication with one or more other state monitoring components. For example, the state monitoring component 206 can attempt to construct or join a mesh network made of up other state monitoring components. In this example, the state monitoring component 206 may utilize a short range wireless communication protocol to establish a network connection with one or more state monitoring components that are within a maximum range. Because the power available from the power supply 208 may be limited, the state monitoring component 206 may be operating on a low power, short range communication path. The alternative network connection can correspond to a portion of the communication network 108 utilized by the set of host computing devices 102 or a completely separate communication network isolated from any communication channel accessible to the host computing devices. In another embodiment, the state monitoring component 206 can continuously maintain the alternative network connection independent of whether a communication event has occurred.

In one embodiment, the state monitoring component 206 will implement a consensus algorithm, such as a Paxos algorithm, to transmit event information to other state monitoring components. In one embodiment, consensus based algorithm can be utilized to determine the condition of the grouping of host computing devices 102. If a consensus can be reached, the various state monitoring components accept the event information as valid. For example, the state monitoring components 206 can agree as to the state of the data centers (operational or nonoperational). In another example, the state monitoring components 206 can exchange control information related to the operation of host computing devices 102, such as whether to initiate a reboot of the host computing devices 102. In another embodiment, consensus based algorithms can be utilized to determine a state monitoring component that will be authoritative for the grouping of host computing devices 102. By way of illustration, state monitoring component 106A can propose to be authoritative for the grouping of host computing devices 102 corresponding to state monitoring components 106B, 106C, 106D, and 106E. If a consensus can be reached, the various state monitoring components accept the event information provided by the designated authoritative state monitoring component as valid

In accordance with a consensus type algorithm, based on the determination of a communication event, the state monitoring component 206 transmits a request to a set of other state monitoring components with a proposal (2). As previously described, the proposal can correspond to a value for the event information that the transmitting state monitoring component 206 wants the receiving state monitoring component 206 to accept or a proposal for designation to be authoritative for the grouping of host computing devices.

Turning to FIG. 3B, in this illustrative embodiment, it is assumed that the state monitoring component 206 can establish communication with a minimum number of other state monitoring components to reach a consensus. If the receiving state monitoring components accept the proposal, the receiving state monitoring component and transmitting state monitoring component exchange additional information to finalize the acceptance of the proposal (4). Illustratively, the exchange of information can correspond to a number of exchanges between the receiving and the transmitting state monitoring components. Once the receiving state monitoring components have accepted a value, the same state monitoring components can transmit the accepted values to other state monitoring components (5).

Referring now to FIGS. 4A-4C, the above interaction between the state monitoring components can be implemented multiple times in a hierarchical approach. For example, a state monitoring component can implement a consensus algorithm among a subset of state monitoring components with a data center to arrive at an accepted value. With reference to FIG. 4A, a data center 400 may be subdivided into multiple sectors 402, 404, 406, and 408. The state monitoring components within each sector of the data center can arrive at a consensus for a value. The same state monitoring components can then implement the consensus algorithm to arrive at an accepted value for all the state monitoring components in a data center. With reference to FIG. 4B, designated state monitoring components in each sector can implement that consensus algorithm to determine an accepted value for the data center. Still further, the same state monitoring components can then implement the consensus algorithm to arrive at an accepted value between various data centers (which have also implemented the consensus algorithm). With reference to FIG. 4C, a state monitoring component in each data center 400A-400E can utilize the consensus algorithm to arrive at the accepted value.

Referring now to FIG. 5, a flow diagram illustrative a control component operating state processing routine 500 will be described. For purposes of illustration, routine 500 will be described as implemented by a state monitoring component 206. However, one skilled in the art will appreciate that routine 500 may be implemented, at least in part, by other components of the host computing device environment 100. In one aspect, the state monitoring component 206 can maintain a default condition that corresponds to a non-fault determination for the host computing device control component 106. If the state monitoring component 206 obtains information associated with the function of the host computing device control component 106, the state monitoring component 206 can determine whether to modify the default state based on the information obtained from the host computing device control component 106. Additionally, if the state monitoring component 206 does not receive any information, it can determine whether to modify the default condition.

At block 502, the state monitoring component 206 sets the current state to a non-fault state. At decision block 504, the state monitoring component 206 determines whether it has received information regarding the operation of aspects of the host computing device environment 100 (which may be exchanged via the consensus algorithm). Illustratively, the information regarding the operation of the host computing device control component 106 can include information regarding processor performance, operating system performance, network performance or power performance information. In one embodiment, the host computing device control component 106 can be configured to transmit the information to the state monitoring component 206. In another embodiment, the state monitoring component 206 can poll the host computing device control component 106 to obtain the information.

If at decision block 504, the state monitoring component 206 determines that it has not received information regarding a fault condition, the state monitoring component 206 sets the current state to a fault condition at block 506. In this embodiment, the failure to receive information from the host computing device control component 106 can be interpreted as a fault condition. The routine 500 then proceeds to block 510, which will be described below.

Referring again to decision block 504, if the state monitoring component 206 had received information regarding the operation of aspects of the host computing device environment 100, the state monitoring component 206 processes the information to determine whether a fault condition exists at decision block 508. Illustratively, the processing of the information associated with the operation of aspects of the host computing device environment 100 (an correspond to a comparison of one or more thresholds that establish the presence of fault conditions. If at decision block 508, the processing of the information regarding the operation of aspects of the host computing device environment 100 is indicative of no faults, the routine 500 returns to block 502.

If at decision block 508, the processing of the information regarding the operation of aspects of the host computing device environment 100 is indicative of a fault condition, the routine 500 proceeds to block 506 where the state monitoring component 206 sets the current state to a fault state. At block 510, the state monitoring component 206 processes the fault condition. Illustratively, the state monitoring component 206 can generate one or more visual indicators based on the determined fault condition. In one embodiment, the state monitoring component 206 can utilize a single visual indicator for any fault condition. In another embodiment, the state monitoring component 206 can utilize multiple visual indicators based on a type of fault condition. For example, the state monitoring component 206 can associate a first color indicator for a fault condition indicative of needed repair fault state and a second color indicator for a fault condition indicative of a troubleshooting fault state. In a further embodiment, the state monitoring component 206 can associate a separate indicator, such as a flashing indicator, that can be associated with a power off condition for the host computing device control component 106. One skilled in the relevant art will appreciate that additional or alternative visual indicators may be implemented. At block 512, the routine 500 terminates.

Turning now to FIG. 6, an event management routine 600 implemented by a state monitoring component 206 for processing event information will be described. Although routine 600 will be described with regard to managing events related to any one of a number of factors associated with the set of host computing devices 102 or the host computing device control component 106, routine 600 may be implemented with regard to the management of other events related to resource usage or resource availability by the set of host computing devices. At block 602, the state monitoring component 206 obtains communication event information and determines a communication event has occurred. As previously described, the communication event can correspond to a determination of errors or faults in the set of host computing devices 102. Alternatively, the communication event can correspond to an exchange of information independent of any determination of errors or faults in the set of host computing devices 102.

At block 604, the state monitoring component 206 attempts to communicate with one or more other state monitoring components via the alternate network connection. In an illustrative embodiment, if a power event (or other event) has been determined, the state monitoring component 206 can assume that the communication network 108 utilized by the set of host computing devices 102 is unavailable or unreliable. Accordingly, the state monitoring component 206 utilizes the communication component 214 to attempt to contact other state monitoring components. As previously described, the alternative network connection corresponds to one or more communication paths, including wireless communication paths (via infrared, RF, optical, terrestrial, satellite communication media, etc.), wired communication paths, or a combination thereof. In one embodiment, if a communication channel has not been previously established, the state monitoring component 206 can attempt to create a new communication channel. Alternatively, the state monitoring components 206 may continuously exchange information via an alternative communication path for purposes of keeping the communication path available or otherwise exchange information.

At decision block 606, a test is conducted to determine whether the state monitoring component 206 has established a connection or is otherwise in communication (based on a pre-existing communication channel) with at least one other state monitoring component. If not, the routine 600 proceeds to block 612, which will be described in greater detail below. Alternatively, if at decision block 606, the state monitoring component 206 is able to establish a connection or access an existing connection with at least one other state monitoring component, at block 608, the state monitoring component 206 transmits a proposal for acceptance of event information. Illustratively, the proposal for acceptance of event information can correspond to a consensus acceptance of a condition for the grouping of host computing devices 102, such as a power level or state, network level or state, and the like. In another embodiment, the proposal for acceptance of event information corresponds to a proposal for a state monitoring component 206 to be designated as authoritative for the grouping of host computing devices 102. In this embodiment, once a state monitoring component has been accepted as authoritative for the grouping of host computing devices, all information related to the a condition for the grouping of host computing devices will be considered as true or accepted by the group.

At block 610, the state monitoring component 206 determines if a consensus has been reached for the state monitoring components 206 that have received the proposal. If a consensus cannot be reached, the value is not accepted. At block 612, if the value is not accepted or a consensus is not reached, in one embodiment, the state monitoring component 206 does not do anything or reverts to another value. For example, the state monitoring component 206 may assume that the other data centers are not functioning. Alternatively, at block 612, if a consensus has been reached, the state monitoring component 206 considers the value to be accepted. At block 614, the routine 600 terminates.

Turning now to FIG. 7, a communication event processing subroutine 700 implemented by a state monitoring component 206 for processing event information will be described. At block 702, the state monitoring component 206 obtains event information from a transmitted state monitoring component 206. At block 704, the receiving state monitoring component 206 processes the received event information. As previously described, a received state monitoring component 206 can receive multiple proposals for a value. In embodiments in which a condition of the grouping is being proposed, the receiving state monitoring component 206 will accept only the proposal with the highest value or most recent value. In other embodiments, the proposal being provided corresponds to designation of the state monitoring component 206 to be designated as authoritative for purposes of deciding the condition associated with the grouping of host computing devices 102. At decision block 706, the state monitoring component 206 determines whether it will accept the received proposal. If so, at decision block 708, the state monitoring component 206 then determines whether it has received a confirmation from the transmitting the state monitoring component 206.

If the state monitoring component 206 does not accept the proposal at decision block 706 or if a confirmation is not received at decision block 708, at block 710, the proposal is rejected. Alternative, if the proposal is accepted and confirmation is received, the state monitoring component 206 can then transmit the accepted value to other state monitoring component 206 at block 712. At block 714, the routine 700 terminates.

It will be appreciated by those skilled in the art and others that all of the functions described in this disclosure may be embodied in software executed by one or more processors of the disclosed components and mobile communication devices. The software may be persistently stored in any type of non-volatile storage.

Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.

Any process descriptions, elements, or blocks in the flow diagrams described herein and/or depicted in the attached figures should be understood as potentially representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process. Alternate implementations are included within the scope of the embodiments described herein in which elements or functions may be deleted, executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those skilled in the art. It will further be appreciated that the data and/or components described above may be stored on a computer-readable medium and loaded into memory of the computing device using a drive mechanism associated with a computer readable storing the computer executable components such as a CD-ROM, DVD-ROM, or network interface further, the component and/or data can be included in a single device or distributed in any manner. Accordingly, general purpose computing devices may be configured to implement the processes, algorithms, and methodology of the present disclosure with the processing and/or execution of the various data and/or components described above.

It should be emphasized that many variations and modifications may be made to the above-described embodiments, the elements of which are to be understood as being among other acceptable examples. All such modifications and variations are intended to be included herein within the scope of this disclosure and protected by the following claims. 

What is claimed is:
 1. A system for managing a plurality of subsets of host computing devices, the system comprising: a first control component in communication with a first subset of the plurality of subsets of host computing devices, the control component including: a management component for monitoring and controlling one or more aspects of the operation of the first subset of the plurality of subsets of host computing devices; and a first state monitoring component configured to monitor a state of the first subset from the plurality of subsets of host computing devices, the first state monitoring component having: a power supply independent of a power supply associated with the control component, a state processing component for determining information regarding at least one communication event information associated with at least one host computing device in the first subset, and a communication interface for establishing communication with other state monitoring components via an alternative communication channel independent of a communication channel associated with the first subset of host computing devices, wherein the at least one communication event comprises a determination of faults; wherein the first state monitoring component implements a consensus based algorithm, via the alternative communication channel, with another state monitoring component that monitors state of a different subset of the plurality of subsets and wherein the implementation of the consensus based algorithm designates a state monitoring component authoritative for the plurality of subsets.
 2. The system as recited in claim 1, wherein the consensus based algorithm corresponds to transmission of a proposal for designation of a state monitoring component as authoritative for one or more of the plurality of subsets of host computing devices.
 3. The system as recited in claim 2, wherein the consensus based algorithm corresponds to a minimum number of state monitoring components accepting the proposal.
 4. The system as recited in claim 1, wherein at least one iteration of the consensus based algorithm corresponds to a subset of the state monitoring components corresponding to a data center.
 5. The system as recited in claim 4, wherein at least one iteration of the consensus based algorithm corresponds to all state monitoring components in the data center.
 6. The system as recited in claim 5, wherein at least one iteration of the consensus based algorithm corresponds to state monitoring components in multiple data centers.
 7. A computer implemented method for managing a plurality of subsets of host computing devices, the method comprising: under control of one or more processors configured with specific executable instructions for implementing a state monitoring component for monitoring a state of a selection from a plurality of subsets of host computing devices, obtaining event information, the event information corresponding to a state of the selection of the host computing devices associated with the state monitoring component; iteratively causing communications via a communication channel with at least one other state monitoring component which monitors a state of a second selection from the plurality of subsets of host computing devices; and determining a state of the plurality of subsets of host computing devices based on a consensus based algorithm including a designation of a state monitoring component authoritative for the plurality of subsets of host computing devices.
 8. The computer implemented method as recited in claim 7, wherein at least one iteration of the consensus based algorithm corresponds to a subset of state monitoring components corresponding to a data center.
 9. The computer implemented method as recited in claim 7, wherein at least one iteration of the consensus based algorithm corresponds to all state monitoring components in a data center.
 10. The computer implemented method as recited in claim 7, wherein at least one iteration of the consensus based algorithm corresponds to state monitoring components in multiple data centers.
 11. The computer implemented method as recited in claim 7, wherein causing communications via a communication channel with at least one other state monitoring component includes causing communications via at least one of a wired and a wireless communication channel.
 12. The computer implemented method as recited in claim 11, wherein communication event information corresponds to power event information.
 13. The computer implemented method as recited in claim 7, wherein iteratively causing communications via a communication channel with at least one other state monitoring component to determine a state of the plurality of subsets of host computing devices includes determining a state monitoring component authoritative for the plurality of subsets of the host computing devices.
 14. A state monitoring component for monitoring a state of a plurality of subsets of host computing devices, the state monitoring component including one or more processors and a power supply, the state monitoring component comprising: a state processing component for determining event information associated with at least one host computing device in a first subset of the plurality of subsets; and a communication interface for communicating with other state monitoring components of the plurality of subsets, via an alternative communication channel independent of a communication channel associated with host computing devices in the first subset; wherein the state monitoring component communicates with at least one other state monitoring component regarding the event information determined by the state processing component, via the alternative communication channel, to implement a consensus based algorithm for determining a state of the plurality of subsets of host computing devices based on the event information, including a designation of a state monitoring component authoritative for the plurality of subsets of host computing devices.
 15. The state monitoring component as recited in claim 14, wherein communicating with other state monitoring components comprising determining a state based on a consensus based algorithm which includes iteratively via the alternative communication channel with the other state monitoring components.
 16. The state monitoring component as recited in claim 15, wherein at least one iteration of the consensus based algorithm corresponds to a subset of state monitoring components corresponding to a data center.
 17. The state monitoring component as recited in claim 15, wherein at least one iteration of the consensus based algorithm corresponds to all state monitoring components in a data center.
 18. The state monitoring component as recited in claim 15, wherein at least one iteration of the consensus based algorithm corresponds to state monitoring components in multiple data centers.
 19. The computer-implemented method as recited in claim 7, wherein event information corresponds to power event information.
 20. The state monitoring component as recited in claim 14, wherein the state monitoring component further comprises a power supply independent of a power supply associated with the host computing devices. 